| 1. | Lock manager requests can be owned by a variety of entities 锁管理器请求可由各种实体所拥有。 |
| 2. | All resources handled by the lock manager are scoped by the database id 由锁管理器处理的所有资源均按该数据库id划分范围。 |
| 3. | The query processor then requests the appropriate locks from the lock manager 然后,查询处理器将向锁管理器请求适当的锁。 |
| 4. | Lock manager properties 锁管理器属性 |
| 5. | Materializing the view does require access to the lock manager internal data structures 具体化该视图需要访问锁管理器的内部数据结构。 |
| 6. | The lock manager properties define server behaviors pertaining to locking and timeouts 锁管理器属性定义与锁定和超时有关的服务器行为。 |
| 7. | The maximum number of locks that can be allocated per session in lock manager is 262143 在锁管理器中可以为每个会话分配的最大锁数是262143 。 |
| 8. | Locks are managed internally by a part of the database engine called the lock manager 锁由数据库引擎的一个部件(称为“锁管理器” )在内部管理。 |
| 9. | The nfs lock manager on the file server holds the locks that are granted to server h on its behalf 文件服务器上的nfs锁定管理器代表服务器h持有锁定。 |
| 10. | The lock manager grants the locks if there are no conflicting locks held by other transactions 如果与其他事务所持有的锁不会发生冲突,锁管理器将授予该锁。 |